home *** CD-ROM | disk | FTP | other *** search
-
-
-
- HMSG 1.05, A Frontend to Harvey's Robot Page 1
-
-
- 1. Warranty
-
- HMSG IS FREELY AVAILABLE, BUT COPYRIGHTED BY Gary A. Mays. Gary A. Mays
- OFFERS NO WARRANTY, EITHER EXPRESS OR IMPLIED, WITH REGARD TO THE USE OF
- HMSG AND HEREBY DISCLAIMS ANY AND ALL IMPLIED WARRANTIES OF
- MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
-
- IN NO EVENT WILL Gary A. Mays BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL
- DAMAGES, INCLUDING, BUT NOT LIMITED TO, DESTRUCTION OF DATA OR DAMAGE TO
- YOUR EQUIPMENT.
-
-
-
-
- 2. HMSG 1.05, A Frontend to Harvey's Robot
-
- HMSG simplifies the use of Harvey's Robot, an inbound/outbound 4d *.PKT
- robot mail system (ROBOT600.ZIP). HMSG is freely available, just as is
- Harvey's Robot. Harvey's robot is available at 1:261/1191 as
- ROBOT600.ZIP. File requests are honored from 6pm until 8am.
-
- HMSG uses an internal configuration to create a temporary configuration
- file for Harvey's Robot for each message. The temporary configuration is
- written to the directory specified in your system's environment variable
- TEMP. If TEMP is undefined, then the root directory of the current drive
- is used. It is recommend that a ram disk be used as the TEMP directory.
-
- HMSG uses unique filenames for the temporary control file. This prevents
- collisions in multitasking environments.
-
- When the default message attributes are configured, a message can be
- sent with only one or two command line switches required:
-
- DIR D:\NEWFILES | HMSG -S"Newfiles" -toss
-
- will send me a message listing newly arrived files. The -toss switch
- calls your configured mail tosser to toss the robot message packet.
-
- HMSG -? will display the help screen. HMSG CONFIG will display the
- configuration screen.
-
-
-
- 3. HELP SCREEN
-
- HMSG v1.04 - Frontend to Harvey's Robot by Gary A. Mays
- Switches:(Activated with - or /, but cannot mix) Config with HMSG CONFIG
- -p:packets-path Inbound for FrontDoor, Inbound or Outbound
- for Binkley.
- -e:packets-extension PKT, OUT, ...
- -area:area-name Default is nothing which is netmail.
- -attr:message-attributes 0=Public, P=Private, A=F'Att, R=F'Req. When
- other no attr are specified, then the default
- is P for netmail and 0 for echomail. A and R
- don't work when from inbound.
- -fn:"from-name" Double quotes required to preserve case and
- when there are imbedded spaces.
-
-
-
-
-
-
- HMSG 1.05, A Frontend to Harvey's Robot Page 2
-
-
- -fa:from-address
- -tn:"to-name"
- -ta:to-address!password !password: 8 character optional packet
- password prefix with !
- -s:subject
- -m:message-file No file outputs single line of ---
- -k Erase the message-file named with the -m
- switch');
- -o:"origin line"
- -toss Toss PKT with configured tosser (HMSG does
- not swap before shell).
- Instead of specifying message text with -M, message text can be piped
- from a program or redirected from a file. Just use:
-
- PGM | HMSG -S"Info"
-
- or
-
- HMSG -S"Subject" <filename
-
- When the piped or re-directed input is empty, then HMSG will abort.
-
- The -toss switch is not used when you have specified an outbound
- directory to receive the mail packet.
-
- The configured 'ECHOMAIL Default From Address' is used as a template for
- the to-address and from-address switches: -ta and -fa. An address
- specified for -ta and -fa can be NODE or NODE.POINT or .POINT, and the
- missing components will be taken from the template.
-
- Parameters not enclosed in double quotes are converted to upper case.
- Parameters that have imbedded spaces must be enclosed in double quotes.
- Commas in all parameters will be stripped out because the robots
- configuration file uses commas to separate the parameters. The colon in
- the parameters is used for readability and is optional. All options
- except -m and -attr are configurable by HMSG CONFIG. HMSG writes a
- temporary configuration file to the directory specified by the
- environment variable TEMP, or to the root directory of the current drive
- if TEMP is not defined.
-
-
-
- 4. MY CONFIGURATION SCREEN
-
-
- HMSG 1.04 - Frontend to Harvey's Robot by Gary A. Mays
- Specify paths without trailing "\"
- Configuration area of D:\BBSUTIL\HMSG.EXE (Prefix Ctrls with Ctrl-P)
-
- Path to Harvey's Robot: d:\harvey
- Path to packets: D:\INBOUND
- Packet extension: PKT
-
- Netmail toss command:
- hstart "Tossing Netmail from H.EXE" /fs /b /c sq386p in
- Echomail toss/scan command:
- hstart "Tossing Echomail from H.EXE" /fs /b /c sq386p in out link squash
-
-
-
-
-
-
- HMSG 1.05, A Frontend to Harvey's Robot Page 3
-
-
-
- Default Area name (blank for netmail):
- Default From name: Sysop
- NETMAIL Default From address (A point of your address): 1:261/1191.1
- ECHOMAIL Default From address (Your address): 1:261/1191
- Default To name: SysOp
- Default To address (Your address): 1:261/1191
- Default Subject: Sysop message
- Default Origin line: Gary's Desk * Baltimore MD * USA
-
-
-
-
- 5. HINTS
-
- I have not tested the use of Harvey's Robot with BinkleyTerm. You may be
- able to set the packet name to OUT, CUT, HUT or whatever and place the
- packet into your outbound. I use FrontDoor which does dynamic
- scheduling. It's packet area is modified on the fly and cannot accept
- packets placed there by another program.
-
- I have H.EXE create PKTs in my inbound. Messages that are tossed from
- the inbound are not flagged as Local. FrontDoor will not forward
- non-local messages from your own address. To send netmail to another
- node, I had to specify a FROM address other than my own primary net
- address (I used .700 of my primary address).
-
- If you have more than one message to be generated from the same address,
- HR will just add to the packet in the inbound.
-
- HMSG does not swap when exec'ing a command. H.EXE does not need much
- memmory, so it works OK. If you use the -toss switch to call the
- configured tosser, your tosser may not have enough memory to operate. If
- you are using OS/2, you can use HSTART to start a task to process the
- inbound.
-
-
-
- 6. BinkleyTerm Netmail
-
- If you use BinkleyTerm you may only have to specify your outbound as the
- packets directory and specify OUT or CUT or something as the packet
- type. Your tosser would not be involved.
-
-
-
- 7. BinkleyTerm EchoMail
-
- If you use BinkleyTerm and you create an echomail message and want it to
- appear in your echomail area, you must place a PKT in your inbound and
- process it with your tosser just as I do with FrontDoor.
-
-
-
-
-
-
-
-
-
-
-
-
- HMSG 1.05, A Frontend to Harvey's Robot Page 4
-
-
- 8. Examples
-
-
-
- 8.1. Send a text file as a message
-
-
- hmsg -s"Here is your info" -ta1:261/1191.2 -toss -mfile.txt
-
-
- 8.2. Send a weekly mail history report
-
-
- mailhist -dlastweek -a.2 |hmsg -s"Mail history" -ta1:261/1191.2 -toss
-
- MAILHIST creates a report from FrontDoor's history files.
-
-
- 8.3. Send list of non-message/non-tic'ed inbound files
-
-
- showfile d:\inbound |hmsg -s"Non-mail files" -toss
-
- SHOWFILE.EXE does not produce an output when the output is re-directed
- AND there are no non-mail/non-tic'ed files. This allows HMSG to abort
- the message.
-
-
- 8.4. Send report of errors in ALIAS.TXT
-
-
- valias d:\misc\alias.txt|hmsg -s"Bad alias definitions" -toss
-
- VALIAS.EXE does not produce an output when the output is re-directed AND
- there are no errors. This allows HMSG to abort the message.
-
-
- The latest versions of the programs MAILHIST, SHOWFILE, and VALIAS are
- available from the author's system by the same magic name as the main
- .EXE.
-
-
-
-
- Gary A. Mays 1:261/1191@fidonet
- 5248 Reisterstown Rd #1
- Baltimore, MD 21215
-
-
-
-
-
-
-
-
-
-
-
-
-
-